Present Environmental Data with source-aware positioning and stable installation identity - #3

Delivery

• Brand only the dataset discovery/matching plugin as Environmental Data. Keep the marketplace and other product brands unchanged; repository placement remains in the existing HiQ-AI/plugins repo.
• Use Cortex catalog name and native plugin/marketplace displayName for the public name. Keep querying-lca-datasets-expert as stable install identity and querying-lca-datasets as the CLI command. Bump only the plugin package to 0.5.2 for branding/docs delivery; CLI remains 0.5.1 with unchanged archives, digests, skill/agent IDs and authentication requirements.
• Update the generated README projection, dedicated plugin guide, agent/skill descriptions and shared documentation labels.
• Document a dated inventory from the anonymously readable service source catalog: source codes, latest advertised versions, system models, service access flags and LCIA coverage. Do not equate directory visibility with numerical access, free flags with redistribution rights, or unlisted databases with integrations. Remove the old guide wording that could confuse this brand update with a CLI credential-storage migration.

Verification and evidence

• Read the actual Cortex catalog type: user-visible name is separate from stable id. Claude Code 2.1.317 strict validation accepts displayName in plugin and marketplace manifests; an unknown-field control is rejected in strict mode.
• Native marketplace and changed plugin strict validation pass with no manifest errors/warnings. Static generation, component/reference checks, relative links, sensitive-text screening and diff checks pass.
• Compared against the previous catalog: the CLI supply object and authentication/requirements declarations are unchanged; every other product entry is unchanged. Generated projections preserve stable IDs and match public display names.
• Source inventory read by anonymous GET of the existing public /api/relic/sources endpoint on 2026-11-04. No search, dataset-value request, model call, login or write was performed. Not claiming per-account access or lookup acceptance for every listed source.

Consumer and rollout boundary

Native marketplace consumers can display the supported displayName; Cortex catalog consumers use name. Hosts may still show technical IDs in installation commands. No independent reviewer assigned; no required review bypassed. No new repository, service integration, CLI release, Desktop production source switch or Desktop release.

🤖 Generated with Claude Code